System for changing setup of first device that executes predetermined function by second device and these devices

ABSTRACT

The user of an objective device registers a favorite setup of the objective device in a user setup data recording device in correspondence with user information based on a physical feature. Upon detecting the physical feature of the user, the objective device sends its device ID to the user setup data recording device together with the user information based on the physical feature. The user setup data recording device sends setup data of the objective device, which is set in advance by the user, to the objective device on the basis of the received user information and device ID. The objective device changes its setup on the basis of the received setup data.

FIELD OF THE INVENTION

The present invention relates to a system for changing the setups of afirst device, which executes a predetermined function, by a seconddevice, and these devices.

BACKGROUND OF THE INVENTION

Conventionally, many devices allow information setups corresponding touser's requests and favor. For example, in a digital camera, manyfunctions such as an aperture, shutter speed, white balance, exposuretime, the way flash light is emitted, self-timer time duration,presence/absence of date insertion, and the like can be set incorrespondence with user's favor.

Also, a system that can record several patterns of setup data in adevice is available. When the user selects one of several patterns ofsetup data via some user interface, information is set in the device onthe basis of the selected setup data.

However, in the prior art, when many users use a single digital camera,and want to set it according to their favors, each user must manuallyre-input setup data. Furthermore, once a given user sets the digitalcamera according to his or her favor, if another user sets up thedigital camera again, that user must also manually set up the cameraagain.

That is, currently available devices can be set according to user'sfavor. However, when another user sets up a given device again, a givenuser must set up that device again according to his or her favor. Suchcase frequently occurs when a plurality of users use a common device.

The aforementioned system that can record several patterns of setup dataforces the user to select one pattern. Furthermore, since the system canonly record several patterns of setup data, it cannot cope with a casewherein many unspecific users want to use that device with optimalsetups.

SUMMARY OF THE INVENTION

It is an object of the present invention to allow easy setups of adevice.

It is another object of the present invention to obviate the need foruser's manual re-setup process every time the user re-uses the devicewhich has been set once.

It is still another object of the present invention to identify a userwho operates a device, and execute different processes for respectiveusers.

Other features and advantages of the present invention will be apparentfrom the following description taken in conjunction with theaccompanying drawings, in which like reference characters designate thesame or similar parts throughout the figures thereof.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram showing the arrangement of an informationsetting unit built in a digital camera as an objective device;

FIG. 2 is a block diagram showing the arrangement of a user setup datarecording device;

FIGS. 3A and 3B show a state wherein the user sets up various functionsof a digital camera;

FIG. 4 is a diagram showing setups of functions done between user setupdata recording devices and objective devices;

FIG. 5 is a timeline diagram between devices upon registration;

FIG. 6 is a flow chart showing the registration/setup processingsequence in the objective device;

FIG. 7 is a table showing data to be sent from the objective device tothe user setup data recording device upon registration;

FIG. 8 is a flow chart showing the registration/setup processingsequence in the user setup data recording device;

FIGS. 9A and 9B are timeline diagrams between devices upon setting usersetup data again;

FIG. 10 is a table showing data to be sent from the objective device tothe user setup data recording device when broadcast is not made;

FIG. 11 is a table showing user setup data to be sent from the usersetup data recording device to the objective device as a reply uponsetting;

FIG. 12 is a flow chart showing the registration/setup processingsequence in the second embodiment;

FIG. 13 is a flow chart showing the registration/setup processingsequence in the third embodiment;

FIG. 14 is a block diagram showing characteristic functions of aninformation processing system according to the fourth embodiment of thepresent invention;

FIG. 15 is a block diagram showing another arrangement of an objectivedevice 1;

FIG. 16 is a block diagram showing still another arrangement of theobjective device 1;

FIG. 17 is a block diagram showing the overall arrangement of a systemupon externally executing a level classification process according toeach embodiment;

FIG. 18 is a block diagram showing the overall arrangement of a systemupon externally executing a level classification process according toeach embodiment;

FIG. 19 is a flow chart showing the operation of the objective device 1of the fourth to ninth embodiments;

FIG. 20 is a flow chart showing the operation of the objective device 1of the fourth embodiment;

FIG. 21 shows the format of a database present in the objective device 1or an authentication server 3;

FIG. 22 is a block diagram showing characteristic functions of aninformation processing system according to the fourth to seventhembodiments of the present invention;

FIG. 23 shows the format of a database present in a user setup datarecording device 2;

FIG. 24 is a flow chart showing the operation of an objective device 1according to the fifth to seventh embodiments;

FIG. 25 shows the format of a database present in an authenticationserver 3 according to the sixth embodiment;

FIG. 26 is a block diagram showing characteristic functions of aninformation processing system according to the eighth embodiment of thepresent invention;

FIG. 27 is a flow chart showing the operation of an objective device 1of the eighth embodiment;

FIG. 28 is a block diagram showing characteristic functions of aninformation processing system according to the ninth embodiment of thepresent invention;

FIGS. 29A and 29B show the format of a database present in a user setupdata recording device 2 according to the ninth embodiment;

FIG. 30 shows an image of how processing is executed according to theninth embodiment;

FIG. 31 is a flow chart showing the operation of an objective device 1of the ninth embodiment;

FIG. 32 shows the format of data to be sent to the user setup datarecording device 2 according to the ninth embodiment;

FIG. 33 shows another format of data to be sent to the user setup datarecording device 2 according to the ninth embodiment;

FIG. 34 shows an example of data to be sent from the user setup datarecording device to the objective device when the objective device is anetwork connection device;

FIG. 35 shows an example of data to be sent from the user setup datarecording device to the objective device when the objective device is aprinter;

FIG. 36 shows an example of data to be sent from the user setup datarecording device to the objective device when the objective device is adevice which is connected to a network via an access point;

FIG. 37 shows an example of data to be sent from the user setup datarecording device to the objective device when the objective device is avehicle seat; and

FIG. 38 shows an example of data to be sent from the user setup datarecording device to the objective device when the objective device is amassage chair.

DESCRIPTION OF THE PREFERRED EMBODIMENTS

Preferred embodiments of the present invention will be describedhereinafter with reference to the accompanying drawings. In thisembodiment, a device in which information is to be set is called an“objective device”, and a device which saves setup data of variousobjective devices and sets the data in the objective devices is called a“user setup data recording device”.

The user setup data recording device of this embodiment is of wristwatchtype, and the user wears it on a wrist. On the other hand, the objectivedevice is a digital camera, which can be adjusted according to setupdata by operating motors and the like on the basis of the setup datareceived from the user setup data recording device. Furthermore, afingerprint sensor that measures a personal feature is used as a sensor.

[First Embodiment]

FIG. 1 is a block diagram showing the arrangement of an informationsetting unit built in a digital camera as an objective device. Anobjective device 1 has an information setting unit in which a CPU 101,ROM 102, pattern matching unit 103, data converter 104, startup ROM 105,flash ROM 106, fingerprint sensor 107, data receiver 112, and datatransmitter 113 are connected to a bus. The fingerprint sensor 107detects a fingerprint when a finger 4 is pressed against it. The datareceiver 112 and data transmitter 113 are connected to a wirelessinterface (I/F) 111, and exchange data with a user setup data recordingdevice 2 via a wireless channel 5. The objective device 1 has a powersupply unit 191, which is connected to a power supply 192, and supplieselectric power to respective units.

FIG. 2 is a block diagram showing the arrangement of the user setup datarecording device. The user setup data recording device 2 has anarrangement in which a CPU 201, RAM 202, flash ROM 203, startup ROM 204,data receiver 212, and data transmitter 213 are connected via a bus. Thedata receiver 212 and data transmitter 213 are connected to a wirelessinterface (I/F) 211, and exchange data with the objective device 1 viathe wireless channel 5. The user setup data recording device 2 has apower supply unit 291, which is connected to a power supply 292, andsupplies electric power to respective units.

FIGS. 3A and 3B show a state wherein the user sets up various functionsof the digital camera. As illustrated in FIG. 3A, when a fingerprint isdetected by the fingerprint sensor 107 provided to a shutter button 8upon pressing the shutter button 8 of the digital camera as theobjective device 1, the objective device 1 receives setup data from theuser setup data recording device 2. As shown in FIG. 3B, zoom adjustmentis done according to the received setup data.

FIG. 4 shows setups of functions done between user setup data recordingdevices and objective devices. For example, when the user setup datarecording device 2 is user setup data recording device A (2 a), theobjective device 1 becomes objective device A (1 a) in which setup datafrom user setup data recording device A (2 a) are registered, byexecuting the operation shown in FIG. 3A. Likewise, when the user setupdata recording device 2 is user setup data recording device B (2 b) or C(2 c), the objective device 1 becomes objective device B (1 b) or C (1c) in which setup data from user setup data recording device B (2 b) orC (2 c) are registered, by executing the operation shown in FIG. 3A.

[Registration Process]

A process for registering data from the objective device 1 in the usersetup data recording device 2 will be explained first. FIG. 5 is atimeline diagram between the devices upon registration. The registrationsequence includes the following steps A, B, and C.

A. Authentication data is recorded in the user setup data recordingdevice.

The user registers authentication data in the user setup data recordingdevice 2 using a device exclusively used to record authentication dataor the objective device 1. That is, a fingerprint of the user is read bythe fingerprint sensor as physical information, and the read data isconverted into authentication data, which is sent to and recorded in theuser setup data recording device 2 via the wireless channel. Note thatthe read data may be directly used as authentication data.

B. The user manually sets up the objective device.

The user turns on the power supply 192 of the objective device 1 tostart it up. Then, the user manually sets up the objective device 1. Inthis embodiment, since the objective device 1 is the digital camera, theuser manually sets up functions of the digital camera such as a shutterspeed, ON/OFF of AF (auto-focus), film speed (ISO 100/400), and thelike. Since the startup ROM 105 or flash ROM 106 stores a basic set ofdata to be set, the data set by the user (device setup data) arerecorded in the RAM 102.

C. The set device setup data is registered in the user setup datarecording device as user setup data.

FIG. 6 is a flow chart showing the registration/setup processingsequence in the objective device. This processing program is stored inthe startup ROM 105 in the objective device 1, and is executed by theCPU 101.

After the objective device 1 is set in an initial state by turning onthe power supply 192, the user sets up the objective device, and waitsuntil the fingerprint sensor 107 operates (step S1). The user makes aregistration start action, and presses the finger 4 against thefingerprint sensor 107 of the objective device 1. When the fingerprintsensor 107 is activated upon detecting touch with the finger 4, itchecks if the registration start action has been made (step S2).

As the registration start action, for example, the user presses thefinger 4 against the fingerprint sensor 107 while pressing aregistration button equipped on the objective device 1, or the user tapsthe fingerprint sensor 107 twice, and presses the finger 4 against thefingerprint sensor 107 within 5 sec after the second tapping. Note thatthe registration start action is not particularly limited as long as itallows the user to explicitly instruct registration.

In this case, assume that the registration start action has been made,and the objective device 1 records information indicating that datawhich can be registered is to be sent (step S3). On the other hand, ifthe registration start action has not been made, the flow jumps to stepS4.

The objective device 1 checks if the fingerprint sensor 107 can acquireuser's physical information (fingerprint) (step S4). If the physicalinformation can be acquired, the read physical information istemporarily recorded in the RAM 102, is converted into authenticationdata by the data converter 104, and the converted data is recorded inthe RAM 102 (step S5). Note that the physical information may bedirectly used as authentication data without being converted, and thedata conversion process may be skipped. In this case, the physicalinformation must be recorded by the same method as that whenauthentication data is recorded in the user setup data recording device2. When the CPU 101 can perform data conversion, the data converter 104may be omitted. Furthermore, the data conversion process may include asecurity process such as encryption or the like. The convertedauthentication data is stored in the RAM 102.

Note that by the process in step S3 the RAM 102 records informationindicating whether or not the user wants to register. More specifically,information indicating whether or not the user has made registration isrecorded. Also, the RAM 102 records user's authentication data by theprocess in step S5.

The objective device 1 checks with reference to data, which is stored inthe RAM 102 and indicates whether or not registration has been made, ifthe authentication data is sent as data that can be registered (stepS6).

In this case, since the user has made the registration action, and datathat can be registered is to be sent, the authentication data stored inthe RAM 102, device ID data registered by the manufacturer of theobjective device in the startup ROM 105 or flash ROM 106, and devicesetup data manually set in the RAM 102 by the user are sent to the usersetup data recording device 2 (step S7). FIG. 7 shows data to be sentfrom the objective device to the user setup data recording device uponregistration.

FIG. 8 is a flow chart showing the registration/setup processingsequence in the user setup data recording device. This processingprogram is stored in the startup ROM 204 in the user setup datarecording device 2, and is executed by the CPU 201.

The user setup data recording device 2 is in an initial state. Uponreceiving data sent from the objective device 1 (step S31), it ischecked if the received data contains device setup data (step S32). Ifthe device setup data is contained, that data is recorded in the usersetup data recording device 2 as user setup data. The user setup datarecording device 2 searches the contents of the flash ROM 203 using thereceived device ID data as a key, and if user setup data has alreadybeen recorded in correspondence with the received device ID, the device2 overwrites the received device setup data on that user setup data(step S33). If user setup data corresponding to the received device IDis not found, the device setup data is recorded in the flash ROM 203 incorrespondence with the received device ID (step S33). After that, theflow returns to step S31.

[Re-setup Process]

The overall process upon setting again the user setup data stored in theuser setup data recording device 2 in the objective device 1 will beexplained below. FIGS. 9A and 9B are timeline diagrams between thedevices upon setting user setup data again. FIG. 9A shows a case whereinthe objective device has already stored corresponding user setup data,and FIG. 9B shows a case wherein the objective device does not store anycorresponding user setup data.

The objective device 1 reads physical information data. The read data isconverted into authentication data. If the objective device 1 canbroadcast data, it sends only device ID data. Note that “broadcast”means communications with all of a plurality of user setup datarecording devices 2 that can communicate with the objective device 1 ifsuch devices 2 are present around the device 1. If the objective device1 does not broadcast data, it sends the authentication data and deviceID data. The objective device 1 records information indicating if itbroadcasted data.

The user setup data recording device 2 searches data in the user setupdata recording device 2 using the received device ID data as a key. Ifuser setup data corresponding to the objective device 1 is found, thedevice 2 sends that user setup data and device ID data. On the otherhand, if user setup data corresponding to the objective device 1 is notfound, the device 2 sends no data.

If the objective device 1 broadcasts data, it receives a plurality ofreplies. The CPU 101 of the objective device 1 statistically processes aplurality of received user setup data, and sets the statisticallyprocessed setup data again. On the other hand, if the objective device 1does not broadcast data, since it receives only one data, the device 1makes a re-setup process based on the single user setup data. Suchre-setup process is done in the following steps D, E, and F.

D. The objective device 1 sends device ID data alone or device ID dataand authentication data to the user setup data recording device 2.

As shown in FIG. 6 above, the user sets the objective device 1 in aninitial state by turning on its power supply 192. The user presses thefinger 4 against the fingerprint sensor 107 of the objective device 1.When the fingerprint sensor 107 is activated upon detecting touch withthe finger 4 (step S1), it checks if a registration start action hasbeen done (step S2). In this case, assume that the registration startaction has not been done. Since the fingerprint sensor 107 is combinedwith the shutter button 8, as shown in FIG. 3A, the user touches thefingerprint sensor 107 which starts the re-setup process without his orher knowledge. Note that the user turns off the fingerprint sensor 107in advance when he or she does not want to set data again.

As described above, since the registration start action is not made inthis case, it is directly checked if physical information can be read(step S4). If read has failed, the control returns to the initial state.On the other hand, if read has succeeded, the read data is temporarilysaved in the RAM 102, and is converted into authentication data by thedata converter 104 (step S5). If fingerprint information is directlyused in personal identification without being converted intoauthentication data, this data conversion process may be skipped. Whenthe CPU 101 can perform data conversion, the data converter 104 may beomitted. Furthermore, the data conversion process may include a securityprocess such as encryption. The converted authentication data is storedin the RAM 102.

Since the registration start action has not been made, it is determinedin step S6 that the data which can be registered is not to be sent, andthe objective device 1 then checks if it broadcasts device ID data (stepS8). Broadcast is made when the objective device 1 collects favors of aplurality of users, and sets data again by statistically processing thecollected favors. Whether or not broadcast is made is determined by themanufacturer of the objective device 1. For example, as the objectivedevice 1 that may be used in a situation wherein broadcast is made, anair conditioner may be used. Note that the user may select whether ornot broadcast is to be made.

If broadcast is made, only the device ID data is sent (step S9). Data tobe sent is obtained by excluding authentication data from data shown inFIG. 10 (to be described later). The objective device 1 recordsinformation indicating if broadcast has been made in the RAM 102.Whether or not broadcast is made is expressed by whether authenticationdata is appended or not to data to be transmitted.

On the other hand, if broadcast is not made, the objective device 1sends the authentication data stored in the RAM 102, and device ID datastored in the startup ROM 105 or flash ROM 106 to the user setup datarecording device 2 (step S10). FIG. 10 shows data to be sent from theobjective device to the user setup data recording device when broadcastis not made.

Since this embodiment uses a wireless communication means, if data ismerely sent using an identical frequency, data is distributed to allobjective devices 1 and user setup data recording devices 2 which arepresent around the source objective device 1.

Therefore, in this embodiment, when authentication data is appended todata to be sent by the objective device 1, the user setup data recordingdevice 2 compares the received authentication data and that held inadvance, and if the two data match, the device 2 starts the searchprocess; if they do not match, the device 2 discards the received data.If authentication data is not contained in data sent by the objectivedevice 1, it is determined that the data is broadcast data, and thedevice 2 unconditionally starts the search process. In this case, theauthentication data also serves as a transmission address.

In this embodiment, since the objective device 1 is the digital camera,broadcast is not made. Upon sending data, the authentication data storedin the RAM 102 is converted into an appropriate communication protocolin the CPU 101, and is sent via the data transmitter 113 and wirelessI/F 111 using the wireless channel 5.

E. The user setup data recording device 2 searches for user setup datacorresponding to the objective device 1, and if user setup datacorresponding to the objective device 1 is found, the device 2 sendsthat data; if corresponding data is not found, the device 2 sends nodata.

As shown in FIG. 8 above, the user setup data recording device 2 is inan initial state. Upon receiving the sent data (step S31), it is checkedif the received data contains device setup data (step S32). If devicesetup data is not contained, the user setup data recording device 2sends corresponding data to the objective device 1.

It is then checked if the received data contains authentication data(step S34). If the authentication data is contained, the receivedauthentication data is collated with that which has already beenregistered in the flash ROM 203 (step S35). This collation is calledpersonal identification. It is checked as a result of personalidentification if two data match (step S36). If two data do not match,the control returns to the initial state, and no data is sent.

On the other hand, if it is determined as a result of personalidentification that two data match, i.e., if it is determined that theuser setup data recording device 2 belongs to the user who is currentlyusing that device, the contents of the flash ROM 203 are searched foruser setup data corresponding to the objective device 1 using thereceived device ID data as a key (step S37).

Since the device ID data contains the manufacturer name, product name,product category name, serial number, and the like, the search is madeusing them as keywords. Normally, the best way of making the search isto use the product name as a keyword. This is because even products ofan identical model, which have different serial numbers, may use usersetup data. However, the serial number or product category may be usedin comparison. The manufacturer of the user setup data recording device2 may determine device ID data to be used in the search or the user mayselect it.

As a result of search in step S37, if corresponding user setup data isnot found, the control returns to the initial state, and no data issent. On the other hand, if corresponding user setup data is found, thefound user setup data and device ID data are sent (step S38). Afterthat, the control returns to the initial state. FIG. 11 shows data to besent from the user setup data recording device to the objective deviceas a reply upon setting.

The received authentication data matches only for a user whose physicalinformation has been acquired by the fingerprint sensor. As a result,even if a plurality of user setup data recording devices 2 are presentaround the objective device 1, data can be consequently sent to the usersetup data recording device 2 of a desired user.

F. When the objective device 1 can receive user setup data within agiven period, it executes a re-setup process on the basis of that usersetup data.

As shown in FIG. 6 above, the objective device 1 waits for reception ofuser setup data within a predetermined period of time (step S11). Ifuser setup data cannot be received, the control returns to the initialstate; otherwise, it is checked if the received data is a reply tobroadcast (step S12).

The objective device 1 recorded in the RAM 102 information indicating ifit broadcasted. Hence, if the objective device 1 broadcasted, thereceived data is processed as a reply to broadcast; otherwise, thereceived data is processed as a reply from a single user.

In step S12, the objective device 1 compares to check if device ID datacontained in the received data matches its own device ID data. If thetwo data match, since the received data is a reply to the data sent bythe objective device 1 itself, the subsequent process is executed;otherwise, the received data is discarded. Note that items of the deviceID data to be actually compared are not specified in the abovedescription, but they may be determined by the manufacturer of the usersetup data recording device 2 or may be of user's choice.

If broadcast was made, a plurality of received user setup data arestatistically processed (step S13), and the objective device 1 executesa re-setup process based on the statistical processing result (stepS14). After that, the control returns to the initial state. On the otherhand, if broadcast was not made, the objective device 1 executes are-setup process based on the received user setup data (step S15), andthe control returns to the initial state. In this embodiment, sincebroadcast was not made, the digital camera executes a re-setup processaccording to user's favor with reference to the user setup data (FIG.11) sent from the user setup data recording device 2.

[Second Embodiment]

In the first embodiment, upon registration in the objective device, theuser makes a registration start action first, then presses a fingeragainst the sensor to generate authentication data, and sends the data.Conversely, the user may press a finger against the sensor to generateauthentication data, and that data may be sent after a registrationstart action is made. In the second embodiment, the latter case will beexplained in detail below.

Since an information setting system of the second embodiment has thesame arrangement as the first embodiment, and only the order of theregistration start action and generation of authentication data isdifferent from the first embodiment, only different processes will beexplained. FIG. 12 is a flow chart showing the registration/setupprocessing sequence in the second embodiment. Since processes in step S5and the subsequent steps are the same as those in the first embodiment,a description thereof will be omitted by assigning the same step numbersthereto.

The user presses the finger 4 against the fingerprint sensor 107 of theobjective device 1 in the initial state, and waits until the fingerprintsensor 107 is activated (step S1). After the fingerprint sensor 107 isactivated, it is checked if physical information (fingerprintinformation) can be sampled (step S2A). If physical information cannotbe sampled, the flow returns to step S1.

On the other hand, if physical information (fingerprint information) canbe sampled, that information is converted into authentication data, andthe converted data is recorded in the RAM 102 (step S3A).

After that, the control waits for a predetermined period of time (stepS3B), and it is checked if a registration start action has been madeduring that period (step S4A). If a registration start action has notbeen made during the predetermined period of time, it is determined thata re-setup process is to be done, and processes in step S6 and thesubsequent steps are executed. On the other hand, if the registrationstart action has been made during the predetermined period of time,information indicating that data which can be registered is to be sentis recorded in the RAM 102 (step S5A), and the flow advances to step S6.

In the second embodiment, the control waits for a predetermined periodof time, if the registration start action has been made during thatperiod, information indicating that data which can be registered is tobe sent is recorded in the RAM 102, and the flow advances to step S6. Onthe other hand, if the registration start action has not been made, theflow jumps to step S6. After a predetermined period of time, it ischecked with reference to the RAM 102 if information indicating thatdata which can be registered is to be sent is recorded.

In this way, authentication data may be generated first, and it is thenchecked if the registration start action has started.

[Third Embodiment]

In the third embodiment, the user presses the finger against the sensorto generate authentication data first, and data is sent after aregistration start action is made, as in the second embodiment. FIG. 13is a flow chart showing the registration/setup processing sequence inthe third embodiment. Note that the same step numbers denote the samestep processes as those in the second embodiment.

That is, after sampled physical information (fingerprint information) isconverted into authentication data, and the converted data is recordedin the RAM 102 in step S3A, the control makes the user explicitly selecta registration start action or re-setup action (step S4B). For example,a registration button and re-setup button are provided to the objectivedevice 1, and the control prompts the user to press one of them.

If the user has pressed the registration button, information indicatingthat data which can be registered is to be sent is recorded in the RAM102 (step S5A), and the flow advances to step S6. On the other hand, ifthe user has pressed the re-setup button, the flow jumps to step S6.Irrespective of the button selected by the user, the objective device 1checks with reference to the RAM 102 in the process in step S6 if datawhich can be registered is to be sent.

In this manner, authentication data may be generated first, and it isthen checked if the registration start action has started or if there-setup action has been made.

[Fourth Embodiment]

This embodiment will explain a case wherein a level classificationprocess for identifying a user who accesses the objective device 1 andexecuting a different process for each user is executed, as shown inFIG. 14. A case will be explained below wherein an authenticationprocess for the user is made as the level classification process.

Also, in this embodiment, objective devices with the arrangements shownin FIGS. 15 and 16 will be explained in addition to the objective device1 shown in FIG. 1.

In the arrangement of an objective device 1 shown in FIG. 15, a LAN I/F114 and modem 115 are added to the arrangement shown in FIG. 1, and thepattern matching unit 103 is excluded therefrom.

In the arrangement of an objective device 1 shown in FIG. 16, a LAN I/F114 and modem 115 are added to the arrangement shown in FIG. 1.

The arrangement of the objective device 1 changes slightly depending onwhether to execute the level classification process inside or outsidethe objective device. When the level classification process is executedinternally, any of the arrangements shown in FIGS. 1, 15, and 16 can beused; when the level classification process is executed externally,either the arrangement shown in FIG. 15 or 16 is used. Of course, whenthe level classification process is externally executed via a wirelesschannel without using the LAN I/F 114 and modem 115, any of thearrangements shown in FIGS. 1, 15, and 16 may be used.

When the level classification process is executed internally, thearrangement of the overall system including the objective device 1 anduser setup data recording device 2 is the same as that shown in FIG. 4.However, when the level classification process is executed externally,the arrangement shown in FIG. 17 or 18 is adopted. In the overallarrangement shown in FIG. 4, objective devices 1 a, 1 b, 1 c, . . . anduser setup data recording devices 2 a, 2 b, 2 c, . . . are connected toeach other via wireless channels. In the overall arrangement shown inFIG. 17, objective devices 1 a, 1 b, 1 c, . . . are connected to theauthentication server 3 via a LAN (Local Area Network) 6 or publicnetwork 7. In the arrangement shown in FIG. 18, an objectivedevice/authentication server 1 aa is provided in place of theauthentication server 3 in the arrangement shown in FIG. 17.

The arrangement of the user setup data recording device 2 is as shown inFIG. 2.

In this embodiment as well, assume that the user wears a wristwatch typeuser setup data recording device 2 on a wrist. The user need not alwayswear the device 2 on a wrist, but must hold it at a position where thedevice 2 can communicate with the objective device 1. A digital cameraincorporates the objective device 1, and is adjusted according to setupdata received from the user setup data recording device 2 by operatingmotors and the like based on the received setup data.

In this embodiment, the digital camera and wristwatch are assumed asforms of the objective device 1 and user setup data recording device 2.However, the present invention can be used when they have other forms.For example, examples of the objective device 1 include an illuminationappliance, sound system, seat, and the like in addition to the digitalcamera, and examples of the user setup data recording device 2 include aportable telephone, PDA (Personal Digital Assistant), portable musicplayer, and the like. Note that items of device setup data exchangedbetween the objective device 1 and user setup data recording device 2differ depending on the types of objective devices 1. For example, whenthe objective device 1 is a sound device, items “tone volume”, “surroundmode type (film theater, hall, and the like)”, “loudspeaker direction”,and the like are used in place of items “shutter speed”, “AF ON/OFF”,and the like.

The operation of the objective device 1 according to this embodimentwill be described below with reference to the flow charts in FIGS. 19and 20. Note that the operation of the user setup data recording device2 is the same as that explained above with reference to FIG. 8. Also,the registration operation is the same as that in the first embodiment.

<Re-setup Operation>

The re-setup operation of this embodiment will be described below.

The flow of overall processes executed in the re-setup operation will bebriefly explained first.

The objective device 1 reads physical information data. The read data isconverted into authentication data. An authentication process is done toauthenticate if the user has the right of use of the objective device 1.When broadcast is to be made, device ID data alone is sent; whenbroadcast is not to be made, authentication data and device ID data aresent. The objective device 1 records information indicating that itbroadcasted data or sent data to a plurality of users.

The user setup data recording device 2 searches data therein using thereceived device ID data as a key. If user setup data corresponding tothe objective device 1 is found, the device 2 sends that data and deviceID data; if such data is not found, the device 2 sends no data.

If the objective device 1 broadcasted or sent data to a plurality ofusers, it receives a plurality of replies. The objective device 1statistically processes a plurality of received user setup data, andexecutes a re-setup process based on the statistical processing result.If the objective device 1 neither broadcasted nor sent data to aplurality of users, since it receives only one data, the device 1executes a re-setup process on the basis of single user setup data.

The flow of the re-setup process will be described in detail below.

The timeline diagram between the devices in the re-setup process is thesame as that shown in FIG. 9.

(1) Generation of Authentication Data by Objective Device 1

Referring to FIG. 19, the objective device 1 is set in an initial stateby turning on the power supply 192. The user presses the finger 4against the fingerprint sensor 107 of the objective device 1. Thefingerprint sensor 107 is activated by detecting that touch (step S1).After the sensor 107 is activated, it is checked if a registration startaction has been made (step S2). Assume that a registration start actionhas not been made in this case.

When the fingerprint sensor 107 is combined with a shutter button, theuser can start a setup process by touching the fingerprint sensor 107without his or her deliberate action. Of course, when the user does notwant to execute a re-setup process proposed by the present invention, heor she need only turn off the sensor.

Physical information is then read (step S4). If read has failed, thecontrol returns to the initial state. On the other hand, if read hassucceeded, the read data is temporarily saved in the RAM 102, and isconverted into authentication data by the data converter 104 (step S5).If fingerprint information is directly used in personal identificationwithout being converted into authentication data, this data conversionprocess may be skipped. When the CPU 101 can perform data conversion,the data converter 104 may be omitted. Furthermore, the data conversionprocess may include a security process such as encryption. The convertedauthentication data is stored in the RAM 102.

(2) Authentication Process of Objective Device 1

An authentication process is done inside or outside the objective device1. When the authentication process is done inside the objective device1, e.g., when fingerprint authentication is done using the patternmatching unit 103, the objective device 1 must have the arrangementshown in FIG. 1 or 16. If authentication is done by the CPU 101 withoutusing the pattern matching unit 103, any of the arrangements shown inFIGS. 1, 15, and 16 may be used irrespective of the presence/absence ofthe pattern matching unit 103.

When the authentication process is done outside the objective device 1using the LAN 6, public network 7, or wireless channel 5, a device thatexecutes fingerprint authentication such as the authentication server 3in FIG. 17 or the objective device/authentication server 1 aa in FIG. 18is required on the network, and the objective device 1 must have afunction capable of accessing such device. When fingerprintauthentication is externally executed, the objective device 1 is addedwith components such as a LAN I/F 114, modem 115, and the like ifnecessary. Of course, if the objective device 1 can communicate with theauthentication server 3 using the wireless I/F 111, the need for the LANI/F 114, modem 115, and the like can be obviated. That is, when theauthentication process is executed outside the objective device 1, theauthentication server 3 need only communicate with the objective device1.

A supervisor of the objective device 1 must set in the objective device1 information indicating whether fingerprint authentication is doneinside or outside the objective device 1, in correspondence with thestructure and operating environment of the objective device 1. In stepS1901, this information is checked. Assume that the objective device 1itself or the external authentication server 3 (including anotherobjective device 1 having an authentication server function) includes adatabase shown in, e.g., FIG. 21.

When fingerprint authentication is executed inside the objective device1, the pattern matching unit 103 compares authentication data, which isgenerated by acquiring fingerprint information by the sensor and isstored in the RAM 102, with authentication data, which are alreadyregistered in the flash ROM 106, thereby checking if the user whooperates the objective device 1 has the right of use of the objectivedevice 1 (step S1904). If the flash ROM 106 stores authentication datawhich matches that in the RAM 102, the user has the right of use of theobjective device 1; otherwise, the user does not have such right.

If fingerprint authentication is done outside the objective device 1,the objective device 1 sends the authentication data to theauthentication server 3 or objective device/authentication server 1 aa(step S1902). The authentication server 3 or objectivedevice/authentication server 1 aa receives the authentication data,authenticates by comparing it with authentication data which areregistered in advance, and sends the authentication result to the sourceobjective device 1. The objective device 1 receives the fingerprintauthentication result (step S1903). It is checked based on the receivedresult if the user has the right of use (step S1904). If the user hasthe right of use, the flow advances to step S2001 in FIG. 20; otherwise,the control returns to the initial state.

(3) Transmission of Device ID Data Alone or Device ID Data andAuthentication Data by Objective Device 1

The objective device 1 then checks if it broadcasts device ID data (stepS2001). Note that “broadcast” means communications with all of aplurality of user setup data recording devices 2 that can communicatewith the objective device 1 if such devices 2 are present around thedevice 1.

Broadcast is made when the objective device 1 collects favors of aplurality of users, and executes a re-setup process by statisticallyprocessing the collected favors. Whether or not broadcast is to be madeis determined by the manufacturer of the objective device 1. As theobjective device 1 that may be used in a situation wherein broadcast ismade, an air conditioner may be used. Note that the user may selectwhether or not broadcast is to be made.

If broadcast is not to be made, the objective device 1 sends theauthentication data stored in the ROM 102 and device ID data stored inthe startup ROM 105 or flash ROM 106 to the user setup data recordingdevice 2 (step S2003). Data to be sent is as shown in FIG. 10.

If broadcast is to be made, the objective device 1 sends device ID dataalone. Data to be sent in this case is obtained by excludingauthentication data from that shown in FIG. 10. Also, various otherbroadcast processes may be used. For example, if a predetermined fieldof data to be sent stores text “broadcast”, it can be determined thatthe data is broadcasted. Also, a flag which is set upon broadcasting maybe prepared as one item of transmission data, and if that flag is 1, itmay be determined that the data is broadcast data; otherwise, the datais not broadcast data.

The objective device 1 records in the RAM 102 information indicating ifbroadcast was made. Whether or not broadcast is made is expressed bywhether authentication data is appended or not to data to betransmitted. Since this embodiment uses a wireless communication means,if data is merely sent using an identical frequency, data is distributedto all objective devices 1 and user setup data recording devices 2 whichare present around the source objective device 1.

Therefore, in this embodiment, when authentication data is appended todata to be sent by the objective device 1, the user setup data recordingdevice 2 compares the received authentication data and that held inadvance, and if the two data match, the device 2 starts the searchprocess; if they do not match, the device 2 discards the received data.Upon receiving broadcast data which does not contain any authenticationdata and in which the broadcast flag is set, the device 2unconditionally starts the search process.

In this way, the authentication data also serves as a transmissionaddress.

In this embodiment, assume that broadcast is not made. Upon sendingdata, the authentication data stored in the RAM 102 is converted into anappropriate communication protocol in the CPU 101, and is sent via thedata transmitter 113 and wireless I/F 111 using the wireless channel 5.

After the data is sent (step S2003), it is checked if identical deviceID data is to be sent to a plurality of users (step S2004). The checkingprocess in step S2004 is effective when the setups of only given groupmembers are to be reflected in a given objective device 1 in place ofsetups of unspecified users within the communication range of theobjective device 1. This process is equivalent to checking in theInternet environment if unicast is to be done a plurality of number oftimes.

If it is determined in step S2004 that the data is to be sent to aplurality of users, the authentication data is replaced by that for thegroup members (step S2005), and the replaced data is sent (step S2003).The authentication data for the group members is set in advance in theobjective device 1. In this embodiment, assume that data is not sent toa plurality of users.

Upon receiving the device ID data and the like sent from the objectivedevice 1, the user setup data recording device 2 sends back user setupdata by executing the processes shown in FIG. 8.

The objective device 1 checks if it can receive the user setup data sentfrom the user setup data recording device 2 within a predeterminedperiod (step S2006). If the objective device 1 cannot receive any datawithin the predetermined period, the control returns to the initialstate without any process.

If the objective device 1 receives the user setup data, it checks basedon information which is recorded in the ROM 102 and indicates whether ornot it broadcasted data or sent data to a plurality of users if thereceived user setup data is a reply to the broadcast data or from theplurality of users, or a reply from a single user (step S2007).

The objective device 1 compares if device ID data contained in thereceived data matches its own device ID data. If the two data match,since the received data is a reply to the data sent by the objectivedevice 1 itself, the subsequent process is executed; otherwise, thereceived data is discarded. Note that items of the device ID data to beactually compared in a search are not specified in the abovedescription, but they may be determined by the manufacturer of the usersetup data recording device 2 or may be of user's choice.

If it is determined in step S2007 that the received data is a reply froma single user, the objective device 1 is set up again based on thereceived user setup data (step S2010), and the control returns to theinitial state.

If the received data is a reply to the broadcast data or from theplurality of users, a statistical process of a plurality of receiveduser setup data is executed (step S2008), and the objective device 1 isset up again based on the statistical processing result (step S2009).After that, the control returns to the initial state.

In this embodiment, since broadcast is not made, the digital camera isset up again according to user's favor with reference to the user setupdata in the data which is sent from the user setup data recording device2, as shown in FIG. 11.

[Fifth Embodiment]

FIG. 22 is a block diagram showing characteristic functions of aninformation processing system according to the fifth embodiment of thepresent invention.

This embodiment will explain a case wherein an objective device 1executes a process corresponding to the level of data received from auser setup data recording device 2, as shown in FIG. 22, as an exampleof a process for identifying a user who accesses the objective device 1,and executing a process for each user. That is, a service which isprovided when a database in FIG. 23 is prepared in the user setup datarecording device 2, and the objective device 1 changes its processaccording to data obtained by searching the database will be explained.

The flow charts showing the operation of the objective device 1according to this embodiment use those shown in FIGS. 19 and 24. Thedifference between FIG. 24 and FIG. 20 used in the fourth embodiment isthat a process in step S2400 is added between steps S2007 and S2010.

The aforementioned differences of this embodiment will be supplemented.

The database shown in FIG. 23 is characterized in that the user setupdata recording device 2 holds use histories for respective device IDdata in addition to authentication data and device ID data. The usehistory is updated when the fingerprint sensor 107 of the objectivedevice 1 responds to the user, data shown in FIG. 10 is sent from theobjective device 1 to the user setup data recording device 2, twoauthentication data match upon comparison, and user setup data is foundby searching data in the user setup data recording device 2 using deviceID data.

For example, assuming that the objective device 1 is a digital camera,and data shown in FIG. 10 is sent, a use history of a key which matchesdevice ID data in FIG. 10 is incremented by 1 in the database shown inFIG. 23. More specifically, use history values corresponding to “CANON”,“Digital Camera”, “Auto Set”, and “ASC-0000001” are incremented by 1,and are updated from 15 to 16, 20 to 21, 43 to 44, and 55 to 56,respectively. Of course, other processes such as a decrement process maybe used in place of the increment process, and the increment value isnot limited to 1. Assume that this process is defined in advance in theuser setup data recording device 2.

When the user setup data is sent from the user setup data recordingdevice 2 to the objective device 1, authentication data, user setupdata, and use history values corresponding to respective keys of deviceID data are sent together.

The objective device 1 receives data (step S2006), and checks if thereceived data is a reply to broadcast data or from a plurality of users(step S2007). In this embodiment, assume that the received data is not areply to broadcast data or from a plurality of users.

The objective device 1 collates the received authentication data withthat temporarily recorded in step S5 in FIG. 19 to check if the receiveddata is a reply from the user who used the objective device 1immediately before the current process (step S2400). If the receiveddata is a reply from that user, a service to be provided to that user isselected with reference to the received use history (step S2400), and asetup process corresponding to the selected service is executed (stepS2010). For example, a discount service for registering charge data bydiscounting it 20% if the use history indicates 10 times or more can beprovided.

As described above, when the user setup data recording device 2 holdsthe database shown in FIG. 23, the following advantages are expectedcompared to a case wherein the database is prepared in theauthentication server 3. The use history can be recorded in the usersetup data recording device 2 independently of whether or not theobjective device 1 is connected to the network. That is, themanufacturer that provides the objective device 1 to the user canprovide services irrespective of the use environment of the objectivedevice 1.

The main feature of this embodiment lies in that the database is held inthe user setup data recording device 2. The database can record not onlythe use history but also the use date, location, and the like dependingon the setups of processes done by the user setup data recording device2.

With the mechanism proposed by this embodiment, the manufacturer of theobjective device 1 or a provider which provides services using theobjective device 1 can provide services irrespective of the settingenvironment of the objective device 1. Also, the use states of users canbe recognized more accurately, and can be reflected in the developmentof products more suitable for user's needs.

Also, since use records can be automatically stored in the user setupdata recording device 2 without any user's operation, the user neverforgets to count the number of times of use, and can have manyopportunities of receiving better services from the manufacturers andthe like.

[Sixth Embodiment]

This embodiment will explain a case wherein a process corresponding tothe level of data received from the user setup data recording device 2is executed, e.g., data corresponding to levels are stored in theauthentication server 3, and different services are provided forrespective users, as shown in FIG. 22, as an example of a process foridentifying a user who accesses the objective device 1, and executing aprocess for each user. The flow charts of the objective device 1 of thisembodiment use FIGS. 19 and 24.

In the fourth embodiment, FIG. 21 is used as an example of the databasein the authentication server 3, and when the user touches the sensor 107of the digital camera (objective device 1), authentication and personalidentification are done to make setups according to the user. Thisembodiment will explain services which can be provided when a databaseshown in FIG. 25 is prepared in the authentication server 3 in additionto that shown in FIG. 21.

More specifically, services provided when the user touches the sensor107 to make the objective device 1 look up the database of theauthentication server 3 that records user information, and executedifferent processes for respective users will be explained.

In the fourth embodiment, when authentication is made outside theobjective device 1, authentication data shown in FIG. 10 is sent to theauthentication server 3. Since the authentication data shown in FIG. 10matches registered data of Taro Yamada in the database shown in FIG. 21,it is determined that the user is Taro Yamada, the user ID is 12345, thegender is male, charge data is 2000 yen, and so forth, and Taro Yamadais authenticated as the user who has the right of use of the objectivedevice 1. In this embodiment, data to be sent from the objective device1 to the authentication server 3 contains authentication data and deviceID data. That is, the data shown in FIG. 10 is sent.

Assume that a database having data shown in FIG. 25 is present in theauthentication server 3. The database need not always be present in theserver as long as it can be accessed by the authentication server 3 onthe network. FIG. 25 shows the user ID for only one user, but theauthentication server 3 can store and manage a plurality of user IDs.

In this embodiment, the authentication server 3 authenticates bycomparing authentication data sent from the objective device 1 with thatwhich is held in advance in the server as in the fourth embodiment. Theauthentication process is to compare authentication data. In thisembodiment, when the database shown in FIG. 21 is looked up usingauthentication data as a key, the user ID and the like can be revealed.When the database is searched using the user ID “12345” as a keyword,user data shown in FIG. 25 is found. At this time, management for eachuser is not limited to the user ID, but other keywords such as the username and the like can be used as long as they can specify the user. Ofcourse, authentication data can be used.

In the database shown in FIG. 25, the user ID “12345” has four sets ofinformation such as use permission device ID data, service level, anduse history. The user ID may have five or more sets of information. Theuse permission device ID data is ID data of the device the user isgranted permission of use. The service level is the level of a servicethe user can receive when he or she uses the use permission device IDdata; S is the highest service level and E is the lowest service level.The service level lowers in the order of S, A, B, C, D, and E. The usehistory indicates the number of times the user used the objective device1 having the use permission ID data.

Hence, the user ID “12345” can use the use permission device ID data“ASC-0000001” at the service level “S”, and the use history indicates“15” times.

The authentication server 3 searches for data corresponding to thelevel, as described above, and sends the service level to the objectivedevice 1. The objective device 1 receives the service level, andtemporarily saves it. After that, upon receiving user setup data via acommunication with the user setup data recording device 2, the objectivedevice 1 executes a process corresponding to the saved service level(step S2400 in FIG. 24).

The process corresponding to the service level includes a process for,e.g., limiting the use time of the digital camera (objective device 1)to one week for the service level S (highest) or to 30 min for theservice level E (lowest). The objective device 1 executes such setup onthe basis of the service level (step S2010).

Personal information such as use permission device ID data, use history,or the like is helpful data for product development and sales of themanufacturer, which can acquire such data without the knowledge of theuser. The service level of the user changes depending on the use historyand the like; when the user repetitively uses an identical product ormanufacturer, the service level rises, and the user can receive betterservices.

For example, assume that the objective device 1 is a digital camera, andthe objective device 1 managed by the authentication server 3 is arental digital camera. The manufacturer lends the user the rentaldigital camera, and can collect a use fee. In this case, when the usermakes registration in the authentication server 3 in advance, he or sheneed only touch the sensor of the digital camera to effect a hireprocess.

More specifically, when the user touches the sensor, authentication datais transferred to the authentication server 3 to execute anauthentication process. At this time, rental data such as a rental time,model, and the like are saved in the authentication server, thuscompleting the rental process.

Also, the number of photos that can be taken by that digital camera isunlimited for the service level S, 40 for A, 20 for B, 10 for C, 5 forD, and 2 for E. In FIG. 25, the user with the user ID “12345” canunlimitedly take photos with a camera corresponding to use permission IDdata “ASC-0000001”, 40 photos with a camera “Auto Set”, 20 photos with acamera “Digital Camera”, and so forth. In this way, flexible servicelevels can be set based on use permission device ID data. Themanufacturer can recognize the use histories of the respective users andcan provide better services to a user who uses products of thatmanufacturer, and the user can enjoy such services.

The aforementioned mechanism can be variously applied. For example, aservice type may be used in place of the service level, and a servicethat the user receives may be changed depending on that type.Alternatively, charge data may be multiplied by a given discount ratedepending on the use history to provide a bargain service. Also, thedatabase in FIG. 25 may be segmented to save user setup data ofindividual users, and statistical data indicating the ways the objectivedevice 1 is used can be acquired.

Users may be categorized into groups laid down by a service provider,and services corresponding to groups may be provided. For example,different services may be provided depending on whether the user belongsto a male or female group, or whether the user belongs to a courtesy orregular member group. In this way, different services corresponding todifferent groups can be provided.

As described above, according to this embodiment, when the databaseshown in FIG. 25 is added to the authentication server 3, themanufacturer can provide various services, and the user can enjoy suchservices.

[Seventh Embodiment]

This embodiment will explain a case wherein different services areprovided by storing data in the user setup data recording device 2, andchanging the number of data acquired by the objective device 1 for eachuser, as shown in FIG. 22, as an example of a process for identifying auser who accesses the objective device 1, and executing a process foreach user.

For example, assume that device setup data for a given objective device1 contains 10 items (shutter speed, AF ON/OFF, ISO 100/400, and the likeif the objective device 1 is, e.g., a digital camera). A method ofproviding a service that limits the number of items which can be useddepending on users in such circumstance (for example, an objectivedevice 1A allows user α to make setups using all 10 items of theobjective device 1, but allows user β to make setups using only threeitems) will be explained.

The objective device 1 according to this embodiment changes items usedin setups depending on users in step S2400 in FIG. 24. For this purpose,the objective device 1 or the authentication server 3 that cancommunicate with the objective device 1 saves data for ranking users,and processes executed in correspondence with the ranks of users.

For example, the user rank includes S (highest), A, B, C, and D(lowest). In the process corresponding to the user rank, if device setupdata of a given objective device 1 has 10 items, the user of rank S canmake setups of the objective device 1 using all the 10 items, the userof rank A can use 8 items, the user of rank B can use 6 items, the userof rank C can use 4 items, and the user of rank D can use only 2 items.Upon executing this process, the objective device 1 may receive andprocess user setup data of all the 10 items from the user setup datarecording device 2, or may receive only items corresponding to the userrank.

The user ranking method is not particularly limited. For example, a highrank may be given to a user who frequently uses products of themanufacturer of the objective device 1, or a user who has made userregistration. Also, users may be ranked with reference to data such as ause history, and the like described in the above embodiment.

In this way, a service received at an identical objective device 1 canbe changed depending on users. With this function, the manufacturer ordealer of the objective device 1 can provide value-added services.

[Eighth Embodiment]

FIG. 26 is a block diagram showing characteristic functions of aninformation processing system according to the eighth embodiment of thepresent invention.

This embodiment will explain a case wherein a process corresponding tothe level of data to be sent to a user setup data recording device 2 isexecuted, e.g., different services are provided by storing data in theuser setup data recording device 2, and changing the number of data tobe acquired by the objective device 1 for respective users, as shown inFIG. 26, as an example of a process for identifying a user who accessesthe objective device 1, and executing a process for each user.

The flow charts showing the operation of the objective device 1according to this embodiment use FIGS. 19 and 27. The difference betweenFIGS. 20 and 27 is that a process in step S2700 is added. In thisembodiment, the difference will be supplemented.

The seventh embodiment has explained the method of providing servicesthat limit the number of items which can be used depending on users (forexample, device setup data for a given objective device 1 includes 10items, and the objective device 1 allows user α to make setups using all10 items, but allows user β to make setups using only three items).However, this embodiment provides such services by another method.

In this embodiment, data to be sent from the objective device 1 to theuser setup data recording device 2 undergoes a process corresponding toa pertinent level (step S2700 in FIG. 27), and is then sent (stepS2003).

In the process in step S2700, items used in steps are changed. Theobjective device 1 or the authentication server 3 that can communicatewith the objective device 1 saves data for ranking users, and processesexecuted in correspondence with the ranks of users. For example, theuser rank includes S (highest), A, B, C, and D (lowest). In the processcorresponding to the user rank, if device setup data of a givenobjective device 1 has 10 items, the user of rank S can make setups ofthe objective device 1 using all the 10 items, the user of rank A canuse 8 items, the user of rank B can use 6 items, the user of rank C canuse 4 items, and the user of rank D can use only 2 items.

Upon executing this process, the objective device 1 may receive andprocess user setup data of all the 10 items from the user setup datarecording device 2, or may receive only items corresponding to the userrank. This depends on implementation contents of step S2700, i.e.,processes to be done in correspondence with ranks.

The user ranking method is not particularly limited. For example, a highrank may be given to a user who frequently uses products of themanufacturer of the objective device 1, or a user who has made userregistration.

The objective device 1 sends authentication data, device ID data, anddata generated by the process in step S2700 to the user setup datarecording device 2. In this embodiment, only items of device setup datacorresponding to a pertinent rank are sent as data generated in theprocess in step S2700. Upon receiving blank device setup data, the usersetup data recording device 2 returns items and values of user setupdata corresponding to the items of the received device setup data.

The objective device 1 receives the user setup data. At this time, sincethe objective device 1 receives user setup data corresponding to theuser rank, it executes a setup process based on the received items andvalues.

In this way, a service received at an identical objective device 1 canbe changed depending on users. With this function, the manufacturer ordealer of the objective device 1 can provide value-added services.

Since the number of items of device ID data to be sent from theobjective device 1 to the user setup data recording device 2 can bereduced, a high transmission rate and short data processing time can beachieved due to the reduced transmission data size.

[Ninth Embodiment]

FIG. 28 is a block diagram showing characteristic functions of aninformation processing system according to this embodiment.

This embodiment will explain a case wherein data to be sent from anobjective device 1 to a user setup data recording device, and datareceived from the user setup data recording device respectively undergoprocesses corresponding to their respective levels, as shown in FIG. 28,as an example of a process for identifying a user who accesses theobjective device 1, and executing a process for each user. Morespecifically, a service provided when the objective device 1 changes aprocess according to data obtained by searching databases shown in FIGS.29A and 29B which are prepared in the user setup data recording device 2will be explained below.

As shown in the image in FIG. 30, assume that the objective device 1 isan air conditioner, and is set up on the basis of the setups of userswho belong to a given group. These users are ranked. In this embodiment,the group that uses the objective device 1 includes two users, i.e.,user A with authentication data “OijdiOI” and user B with authenticationdata “AoijOJ”. In the objective device 1, authentication data of theseusers are registered as a group.

The flow charts of the objective device 1 according to this embodimentuse FIGS. 20 and 31. The difference between FIGS. 20 and 31 is thatprocesses of steps S3110, S3101, and S3102 are added. In thisembodiment, transmission to a plurality of users is used.

The flow of the processes of this embodiment from a re-setup situationwill be explained in detail below.

The user sets the objective device 1 in an initial state by turning onits power supply 192. User A presses the finger 4 against thefingerprint sensor 107 of the objective device 1. The fingerprint sensor107 is activated upon detecting touch with the finger 4 (step S1). Ifthe sensor is activated, it checks if a registration start action hasbeen done (step S2). In this case, assume that the registration startaction has not been done.

Since the registration start action has not been done, physicalinformation can be read (step S4). If read has failed, the controlreturns to the initial state. The read data is temporarily saved in theRAM 102, and is converted into the authentication data “OijdiOI” by thedata converter 104 (step S5). If fingerprint information is directlyused in personal identification without being converted intoauthentication data, this data conversion process may be skipped. Whenthe CPU 101 can perform data conversion, the data converter 104 may beomitted. Furthermore, the data conversion process may include a securityprocess such as encryption. The converted authentication data is storedin the RAM 102.

Since the registration start action has not been done, no data which canbe registered is sent (step S6).

An authentication process is done inside or outside the objective device1. A supervisor of the objective device 1 must set in the objectivedevice 1 information indicating whether fingerprint authentication isdone inside or outside the objective device 1, in correspondence withthe structure and operating environment of the objective device 1 (stepS1901). In this embodiment, the authentication process is executedinside the objective device 1.

When fingerprint authentication is executed inside the objective device1, the pattern matching unit 103 compares authentication data, which isgenerated by acquiring fingerprint information by the sensor and isstored in the RAM 102 and the registered authentication data stored inthe flash ROM 106 (step S1904). If the flash ROM 106 storesauthentication data which matches that in the RAM 102, the user has theright of use of the objective device 1; otherwise, the user does nothave such right. If the user has the right of use, the flow advances tostep S2001 in FIG. 31; otherwise, the control returns to the initialstate. In this embodiment, user level classification is also done instep S1904. Assume that user A is registered in the objective device 1as level B, and user B who appears later as level S. Therefore, if theauthenticated user is user A, his or her level is classified to level B.

The objective device 1 then checks if it broadcasts device setup data(step S2001).

The objective device 1 records in the RAM 102 information indicating ifbroadcast was made. Whether or not broadcast is made is expressed bywhether authentication data is appended or not to data to betransmitted. Since this embodiment uses a wireless communication means,if data is merely sent using an identical frequency, data is distributedto all objective devices 1 and user setup data recording devices 2 whichare present around the source objective device 1. In this embodiment,assume that broadcast is not to be made.

Then, a process for each user is executed (step S3100). In thisembodiment, since the user who touched the sensor of the objectivedevice 1 is user A, whose rank is B, only an item “temperature” ofdevice setup data of the objective device 1 is reflected in actualsetups.

In this embodiment, since broadcast is not made, the objective device 1sends the authentication data in the RAM 102, device ID data in thestartup ROM 105 or flash ROM 106, and device setup data of only the item“temperature” determined by level B of user A to the user setup datarecording device 2 (step S2003). Data to be sent is as shown in FIG. 32.Upon sending data, the authentication data stored in the RAM 102 isconverted into an appropriate communication protocol in the CPU 101, andis sent via the data transmitter 113 and wireless I/F 111 using thewireless channel 5.

After the data is sent (step S2003), it is checked if identical deviceID data is to be sent to a plurality of users (step S2004). The checkingprocess in step S2004 is effective when the setups of only given groupmembers are to be reflected in a given objective device 1 in place ofunspecified setups within the communication range of the objectivedevice 1.

If it is determined in step S2004 that the data is to be sent to aplurality of users, the authentication data is replaced by that for thegroup members (step S2005), and the replaced data is sent (step S2003).The group members are set in advance in the objective device 1.

In this embodiment, the group that uses the objective device 1 includestwo users, i.e., user A with authentication data “OijdiOI” and user Bwith authentication data “AoijOJ”. In the objective device 1,authentication data of these users are registered as a group. Since userA has operated the sensor of the objective device 1, the objectivedevice 1 sends the data also to user B as a member of the group.

The objective device 1 replaces the authentication data by that for userB (step S2005). The level of user B is registered as S in the objectivedevice 1. The objective device 1 searches for the level of user B usingthe authentication data. The level S of user B is read, and as a processcorresponding to the level S, items “temperature” and “humidity” ofdevice setup data are reflected in actual setups (step S3100). Theobjective device 1 sends data shown in FIG. 33 for user B (step S2003).Since no more group members are registered, NO is determined in theprocess in step S2004, and the control of the objective device 1advances to step S2006 as a reply standby state from the user setup datarecording device 2.

The processes in the user setup data recording device 2 have beenexplained previously with reference to the flow chart in FIG. 8.

In this embodiment, the user setup data recording device 2 possessed byuser A has the database shown in FIG. 29A, and that possessed by user Bhas the database shown in FIG. 29B.

The user setup data recording device 2 possessed by user A receives datashown in FIG. 32, and that possessed by user B receives data shown inFIG. 33. As for user A, since the device setup data includes only theitem “temperature”, the user setup data recording device 2 possessed byuser A sends device ID data, corresponding use history values, and avalue “26” of the item “temperature” of user setup data in FIG. 29A tothe objective device 1. The user setup data recording device 2 possessedby user B sends device ID data, corresponding use history values, and avalue “22” of the item “temperature” and a value “10” of the item“humidity” of user setup data in FIG. 29B to the objective device 1.

The respective user setup data recording device 2 updates use historyvalues corresponding to the device ID data received from the objectivedevice 1. For example, the items of the received device ID data arecompared with those of device ID data already held by the user setupdata recording device 2, and if they match, the corresponding usehistory value is incremented by 1.

The objective device 1 checks if it can receive data sent within apredetermined period (step S2006). If the objective device 1 cannotreceive any data within the predetermined period, the control returns tothe initial state without any process.

Since the objective device 1 recorded in the RAM 102 in step S2001information indicating that it broadcasted data or sent data to aplurality of users, if it broadcasted data or sent data to a pluralityof users, the received data is processed as a reply thereto; otherwise,the received data is processed as a reply from a single user (stepS3102). In this embodiment, the objective device 1 waits for andreceives replies from the user setup data recording devices 2 of users Aand B.

The objective device 1 compares if the device ID data contained in thereceived data matches its own device ID data. If the two data match,since the received data is a reply to the data sent by the objectivedevice 1 itself, and a process is executed; otherwise, the received datais discarded. Note that items of the device ID data to be actuallycompared in a search are not specified in the above description, butthey may be determined by the manufacturer of the user setup datarecording device 2 or may be of user's choice.

If broadcast was not made (step S3102), the objective device 1 is set upagain on the basis of the received user setup data, and the controlreturns to the initial state.

If broadcast was made (step S3102), a plurality of received user setupdata are statistically processed (step S2008), and the objective device1 is set up again on the basis of the statistical processing result(step S2009). The control then returns to the initial state.

In this embodiment, data was not broadcasted but was sent to a pluralityof users. Hence, NO is determined in step S2007, and a process for eachuser is executed in step S3101. The objective device 1 receives only thevalue “26” of the item “temperature” for user A, and the value “22” ofthe item “temperature” and the value “10” of the item “humidity” foruser B in addition to the device ID data and use history valuescorresponding to the items of the device ID data. The level of user A isB, and that of user B is S.

The objective device 1 executes a process corresponding to the userlevel (step S3101). As for humidity, since the objective device 1receives “10” alone as the user setup data of user B, it is set to have“humidity” of “10”%. Then, temperature is set. The setup values oftemperature are received from both users A and B. The levels of users Aand B are compared. If the users have identical level, the sum total ofthe values is simply divided by the number of users. For example, ifusers A and B have identical level, since the received values are “26”and “22”, the objective device 1 is set to attain “24” degrees.

However, user A has rank B, and user B has rank S. Hence, a process thatpreferentially uses the user setup data of rank S is executed. Forexample, “23” degrees may be set to be closer to the user setup data ofuser B with higher rank than “24” degrees as the average of the twousers, or the user setup data of user A is ignored, and “22” degrees maybe set. Although not exemplified, the objective device 1 receives usehistories of the respective users with respect to the objective device1. Hence, the process according to the level may be executed in stepS3101 in consideration of the use histories of the users. For example,user setup data of a user with larger use history values may bereflected in the objective device 1 more easily.

The process executed in step S3101 depends on implementation contents ofthe manufacturer of the objective device 1. This embodiment is oneexample. In the above example, data to be updated by device ID data isthe use history. Of course, other items may be updated. For example, thenumber of times of charge, date, and the like may be updated.

When programs according to the flow charts of the respective embodimentsare stored in, e.g., the flash ROM 106 in the objective device 1 tooperate the objective device 1, the control methods of the aboveembodiments can be implemented.

The objective device 1 and user setup data recording device 2 can beadded with a function of encrypting data to be sent. In this case, adata encryption function is required. Encryption may be done by the CPU101, or a dedicated chip for encryption may be prepared. At the sametime, if data is encrypted, the objective device 1 and user setup datarecording device 2 must have a function of receiving encrypted data, anddecrypting that data. Data decryption may be done by the CPU 101 or adedicated chip for decryption may be prepared. In the present invention,such schemes are not particularly limited.

When data is encrypted, the security of communication data can beimproved compared to a case wherein data is exchanged without beingencrypted. If public key cipher is adopted as an encryption scheme, andthe objective device 1 generates a secret key based on sensorinformation, the data can be used not only in encryption but also inuser authentication and specification of the user setup data recordingdevice 2.

In the above embodiments, the objective device 1 has the sensor 107.This is to assure data security and to use the device as a userinterface. That is, since the objective device 1 comprises the sensor,personal identification and authentication can be made, and the usersetup data recording device 2 cannot be used if it is acquired by athird party, thus protecting setup data which reflects user's favor.

Furthermore, the sensor 107 and level classification means can executeauthentication to identify a user who accesses the objective device 1,and different processes for respective users can be executed. Moreover,a user interface which can set up the objective device 1 in response toonly user's action upon reading the physical information using thesensor can be provided.

When the sensor 107 detects the user, it reads the physical informationof that user to generate authentication data. The objective device 1itself or the authentication server compares the already registeredauthentication data with the generated authentication data to makeauthentication. As a result of authentication, if the user has the rightof use, the objective device 1 executes a process corresponding to thelevel as needed, and sends authentication data, device ID data, and thelike to the user setup data recording device 2. If the user has no suchright, no data is sent.

The user setup data recording device 2 makes personal identification,i.e., checks using the authentication data if the user setup datarecording device 2 is that of the current user. If no problem is foundas a result of personal identification, the user setup data recordingdevice 2 searches for user setup data corresponding to the objectivedevice 1 using the previously received device ID data as a key. If thecorresponding user setup data is found, the user setup data recordingdevice 2 sends the user setup data and device ID data. The objectivedevice 1 receives the user setup data, executes a process correspondingto a level as needed, and executes a setup process on the basis of thereceived user setup data.

Therefore, the user can undergo personal identification andauthentication by reading physical information using the sensor. Thatis, the user can send setups of the objective device 1, which have beenregistered in the user setup data recording device 2 once to theobjective device 1 to set it up, when the sensor detects the user.

In the above embodiments, the digital camera and air conditioner are setup. Electronic devices that can undergo the above setup process are notparticularly limited. For example, the present invention can be appliedto various use objects and use situations such as {circle around (1)}the angle and position of a vehicle seat, {circle around (2)} the angleof the seatback, and the method, strength, and position of massage of amassage chair, {circle around (3)} setups of the tone volume, surroundtype, and loudspeaker direction of a sound device, {circle around (4)}video recording setups of types of programs that are frequently recordedby a video recorder, {circle around (5)} the degree and direction ofillumination of an illumination appliance, {circle around (6)} the leveland temperature of a bath, {circle around (7)} the temperature, windspeed adjustment, and the like of an air conditioner, {circle around(8)} a copying machine and printer, and the like.

For example, when the objective device is a device which is connected toa network to upload data (e.g., a digital camera, digital video camera,or portable telephone), the user setup data recording device sends anupload destination URL (FIG. 34) as user setup data to the objectivedevice, thus uploading data in the objective device to the uploaddestination URL.

For example, if the objective device is a digital camera, when the usertouches the shutter of the digital camera (objective device) with afinger, data shown in FIG. 34 is sent form the user setup data recordingdevice to the digital camera. When the user takes a photo, the digitalcamera looks up an image saving destination URL designated by the usersetup data, and transfers the taken image file. The image file is sent,and is automatically saved.

As a result, the upload destination URL corresponding to the device iscorrectly set, and the user can save a taken image at the designated URLirrespective of a digital camera he or she used to take a photo.

When the objective device is a printer at user's destination (e.g., on astreet corner), and when the user touches an auto print button, the usersetup data recording device sends a URL registered therein by the userto the objective device as user setup data (FIG. 35).

The printer as the objective device downloads and prints data from aserver at the designated URL. With this arrangement, a specificnewspaper or the like can be printed by a nearby printer when the usertouches it.

Hence, the user need only touch the printer to easily print data he orshe ordinarily looks up without any data transfer operation.

When the objective device is a network-connected device notebook PC,portable telephone, PDA, PC, or the like, and when the user touches anetwork connection button, the user setup data recording device sends atelephone number of a dial-up destination, which is registered thereinby the user, to the objective device as user setup data. The objectivedevice can install the dial-up destination designated as the user setupdata as a telephone number of an access point for network connection.

Consequently, the user need only touch the notebook PC at his or herdestination to connect the access point or service provider he or sheordinarily uses.

When the objective device is a driver's seat of a vehicle, and when theuser touches an authentication section of that seat with a finger, theuser setup data recording device sends seat adjustment information,which is registered therein by the user, to the objective device as usersetup data (FIG. 37).

The seat adjusts the angle of a seatback, the up-and-down andback-and-forth positions of the seat, and the angle of a headrest on thebasis of the received data.

As a result, the user need only touch the seat to set the seat accordingto his or her favor.

When the objective device is a massage chair, and when the user touchesan authentication section of that massage chair, the user setup datarecording device sends massage chair adjustment information, which isregistered therein by the user, to the objective device as user setupdata (FIG. 38). The massage chair adjusts the angle of a seatback, theangle of a footrest, the strength of foot vibration, the operation time,massage type, strength, and schedule on the basis of the received data.

As a result, the user can undergo massage with his or her favoritemassage method and schedule.

In the above embodiments, the fingerprint sensor for measuring a featureof a body is used as the sensor. Of course, various other sensors may beused. For example, since the iris pattern of a human eye has a personaldifference as in fingerprints, an iris sensor may be attached to aviewfinder of a digital camera, and when the user looks into theviewfinder, the iris sensor may be activated to generate imageinformation data of the iris pattern or authentication data as converteddata.

Furthermore, as still another embodiment, DNA information contained inhuman hair, sputum, sweat, or the like may be used. Since DNAinformation has a personal difference, a hair, sputum, or sweat sensormay be arranged to read DNA information and to generate authenticationdata. Moreover, since voiceprints also have a personal difference, amicrophone (sensor) may be provided to the objective device to samplevoiceprints from a user's voice and to generate authentication databased on the sampled voiceprint information.

In this embodiment, the digital camera and wristwatch are assumed asforms of the objective device and user setup data recording device.However, the present invention can be applied even when they have otherforms. For example, examples of the objective device include anillumination appliance, sound system, seat, and the like in addition tothe digital camera. Examples of the user setup data recording deviceinclude a portable telephone, PDA, portable music player, and the like.Note that items of device setup data exchanged between the objectivedevice and user setup data recording device differ depending on thetypes of objective devices 1. For example, when the objective device 1is a sound device, items “tone volume”, “surround mode type (Movie,Hall, and the like)”, “loudspeaker direction”, and the like are used inplace of items “shutter speed”, “AF ON/OFF”, and the like.

In FIGS. 1, 2, 15, and 16, the flash ROMs 106 and 203 are used to savedata, but other recording media such as a hard disk drive (HDD) and thelike may be used. Likewise, the data receivers 112 and 212 and datatransmitters 113 and 213 may be replaced by data transceivers whichintegrate them.

Also, the wireless transmission scheme, frequency, type, and the likeare not particularly limited. Furthermore, infrared rays, a wirelessLAN, ultrasonic waves, light, and the like may be used. In thisembodiment, a wireless communication is used as a communication medium,but a wired communication may be used instead. Furthermore, acommunication method using a human body is known, and such method may beused.

Note that the present invention is not limited to the apparatus of theabove embodiments, and may be applied to either a system constituted bya plurality of devices, or an apparatus consisting of a singleequipment. The present invention is also achieved by supplying arecording medium, which records a program code of a software programthat can implement the functions of the above-mentioned embodiments tothe system or apparatus, and reading out and executing the program codestored in the recording medium by a computer (or a CPU or MPU) of thesystem or apparatus.

In this case, the program code itself read out from the recording mediumimplements the functions of the above-mentioned embodiments, and therecording medium which stores the program code constitutes the presentinvention. As the recording medium for supplying the program code, forexample, a floppy disk, hard disk, optical disk, magneto-optical disk,CD-ROM, CD-R, magnetic tape, nonvolatile memory card, ROM, and the likemay be used. The functions of the above-mentioned embodiments may beimplemented not only by executing the readout program code by thecomputer but also by some or all of actual processing operationsexecuted by an OS (operating system) running on the computer on thebasis of an instruction of the program code.

Furthermore, the functions of the above-mentioned embodiments may beimplemented by some or all of actual processing operations executed by aCPU or the like arranged in a function extension board or a functionextension unit, which is inserted in or connected to the computer, afterthe program code read out from the recording medium is written in amemory of the extension board or unit.

As a case (prior art) combined with fingerprints described in the aboveembodiments, a technical article “user interface based on fingerprintrecognition” (“Interaction “99”, pp. 169–176, March, 1999) is known. Inthis article, a technique “Finger Storage (Finger Memo)” has beenproposed. As a feature of “Finger Storage”, “data can be copied betweendifferent terminals via a finger”.

However, as a practical implementation method of “Finger Storage”, “whena finger touches another terminal, matching is made with a fingerprintpattern in a Finger ID Table, and a data object corresponding to thatfinger is acquired via a network”. “Finger Storage” holds pairs offingerprint patterns and data as the Finger ID Table, and a fingerprintpattern is used to search for data. In other words, when onlyfingerprints of hands are used, a maximum of 10 pairs can only be held.

By contrast, the present invention is not limited to 10 pairs unlike“Finger Storage” since the fingerprint and data are not paired. Thepresent invention uses device ID data (e.g., a serial number, productname, and the like) as a search key upon searching for data saved in theuser setup data recording device, while “Finger Storage” searches fordata using a fingerprint pattern as a key.

As described above, according to the present invention, the need foruser's manual re-setup operations every time the user uses a device heor she set it once can be obviated. Also, the user is free from anyaction for selecting data from several patterns of setup data.

The supervisor or the like of the objective device (electronic device)can limit user's access to the objective device without impairing user'soperability. With this access limitation, different services can beprovided for respective users.

As many apparently widely different embodiments of the present inventioncan be made without departing from the spirit and scope thereof, it isto be understood that the invention is not limited to the specificembodiments thereof except as defined in the appended claims.

1. A system having a plurality of devices, comprising: firsttransmission means for transmitting specific information of a firstdevice to a second device; second transmission means for transmittingsetup data according to the specific information transmitted by saidfirst transmission means to the first device; change means for changinga setup of the first device upon executing a predetermined function onthe basis of the setup data transmitted by said second transmissionmeans; and acquisition means for acquiring identification information ofa user who uses the first device, wherein said first transmission meanstransmits the specific information together with the identificationinformation acquired by said acquisition means, and wherein saidacquisition means acquires physical information of the user.
 2. Thesystem according to claim 1, wherein said first transmission meanstransmits the specific information together with identificationinformation that specifies a user of the first device.
 3. The systemaccording to claim 2, wherein said second transmission means transmitsthe setup data in accordance with the identification informationtransmitted by said first transmission means.
 4. The system according toclaim 1, wherein the setup data transmitted by said second transmissionmeans can be registered from the first device in the second device.
 5. Afirst device which can execute a predetermined function, comprising:transmission means for transmitting specific information of said firstdevice to a second device; reception means for receiving setup datatransmitted by the second device in accordance with the transmittedspecific information; change means for changing a setup upon executingthe predetermined function on the basis of the setup data received bysaid reception means; and acquisition means for acquiring identificationinformation of a user who uses said first device, wherein saidtransmission means transmits the specific information together with theidentification information acquired by said acquisition means, andwherein said acquisition means acquires physical information of theuser.
 6. The device according to claim 5, wherein said transmissionmeans transmits the specific information together with identificationinformation that specifies a user of said first device.
 7. The deviceaccording to claim 5, further comprising: registration means forregistering the setup data in the second device.
 8. A second devicewhich can change a setup of a first device, comprising: reception meansfor receiving specific information of the first device transmitted bythe first device; transmission means for transmitting setup data inaccordance with the specific information received by said receptionmeans, wherein the setup data to be transmitted by said transmissionmeans is data used by the first device to change a setup upon executinga predetermined function, and wherein the specific information isphysical information of a user who uses the first device.
 9. The deviceaccording to claim 8, wherein said transmission means transmits thesetup data in accordance with identification information that specifiesa user of the first device transmitted from the first device.
 10. Thedevice according to claim 8, wherein the setup data is data registeredby the first device.